Hot Desking - Programming Overview

To program Hot Desking on devices, you must:

Hot Desking is supported on single nodes and on network clusters, and can be programmed using the System Administration Tool. Hot Desking in a network cluster requires RDN Synchronization.

IMPORTANT: If the host ICP is not part of a cluster (that is, it is a standalone system), you must assign it a PBX Number with the local IP address of the controller in the ICP/PBX Networking form. Then, assign this PBX Number as the CEID in the Cluster Elements form.

Planning

Hot desk sets are typically shared phones intended for hot desk users. When no user is logged in, it is recommended that the set provide only basic service such as emergency and operator calls.

NOTE: 5604, 5607, and 5614 wireless phones can only initiate calls using the handset Alarm button when no user is logged in.

Supported sets are provisioned for Hot Desking by assigning the phone a COS that allows hot desk login and logout.

NOTE: As of MiVoice Business 7.0, you have the option to use a simplified and faster installation and auto-provisioning method to deploy Userless Devices that allow hot desk login but do not require a license. With this method, a device can be registered and put into service simply by entering the Set Registration Access Code to initiate the registration. Specifying the device's directory number is not required. See Registering and Auto-provisioning Multiline IP telephones without a DN for details.

Hot desk users are assigned DNs and PINs through the Multiline IP Sets or User and Services Configuration form. When programming feature keys for hot desk users, keep in mind that the hot desk user profiles support 13 programmable keys. If a user logs in to a hot desk set that supports fewer than 13 feature keys the extra keys are not accessible.

If one of these "inaccessible" keys is programmed as a line appearance, calls for the line appearance will still ring at the phone. To avoid "phantom" ringing on hidden line appearances, do one of the following:

NOTES

 

Remote logout is intended to allow administrators, attendants, or help desk personnel to log users out remotely. Remote logout is enabled on any device supporting feature access codes by assigning the phone a COS that allows remote logout.

Hot desk login is invoked by entering a feature access code or pressing a softkey. To allow login and logout on hot desk phones without softkeys, program feature access codes (FACs) for hot desk login, logout, and remote logout. To ensure that users can access all hot desk phones on a cluster, program the same FACs on each node in the cluster.

Resilient Hot Desking follows the existing licensing rules for Hot Desking and resiliency. The licensing and hardware requirements for a single user and a single phone are summarized in the following table:

 

Host (Primary) ICP

Secondary ICP (Resiliency)

Hot Desk User

IP User License

1

0

PLID

1

1

For example, to program 350 hot desk sets and users, you would require 350 IP User Licenses on the host or primary ICP. However, to program 350 hot desk users on a secondary ICP, you would not require any user or device licenses. See About IP User and Device Licenses for more information.

Hot Desk PIN Security ensures that all hot desk users have strong PINs by forcing them to create PINs that adhere to a controlled level of security. A hot desk user who logs in with a weak PIN is automatically routed to the IVR system in MiCollab Nupoint UM for a PIN change. Each hot desk user that uses this feature must have a voice mailbox on the MiCollab Nupoint UM system. Enable and program Hot Desk PIN Security using the Call Coverage Services form.